Method and apparatus for specification of transaction failures in a network management protocol

ABSTRACT

Method and apparatus for managing a network using one or more diagnostic objects in a Management Information Base (MIB). The one or more diagnostic objects include a diagnostic table object for storing data, including diagnostic text information. The method includes receiving a network management protocol command at a managed device in a network, and determining whether the network management protocol command was processed successfully at the managed device. If the network management protocol command was not processed successfully at the managed device, then the method further includes storing data related to the network management protocol command that was not processed successfully at the managed device.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to commonly assigned U.S. Provisional Patent Application No. 60/537,498, filed on Jan. 20, 2004, which is incorporated herein by reference in its entirety.

BACKGROUND

The following disclosure relates to network devices and network communication.

Network management generally takes place between two types of systems, systems in control—called network management systems (NMS), and observed/controlled devices—called managed devices. Managed devices can include, e.g., hosts, servers, routers, repeaters, switches, and computers.

A management protocol is generally used to convey management information between a network management system and a managed device. One example management protocol is the Simple Network Management Protocol (SNMP). SNMP provides a way for network management systems to organize a large amount of information needed to manage a variety of managed devices.

A managed device typically includes specialized software modules, called agents, that access information about the managed device, and make the information available to a network management system. Managed devices maintain values for a number of variables and report the variables, as required, to a network management system. For example, an agent might report the number of bytes and packets in and out of a particular managed device, or the number of broadcast messages sent and received. In the SNMP Network Management Framework, each of these variables is referred to as a managed object. In the context of SMNP, a managed object represents anything that can be managed, or anything that an agent can access and report back to a network management system. A managed object can have a name, one or more attributes, and include a set of operations that can be performed by the managed object. Managed objects are typically contained in a Management Information Base (MIB), a database of the managed objects.

A network management system can control a managed device by sending an SNMP command to an agent of the managed device requiring the managed device to, for example, change the value of one or more variables. Commonly used SNMP commands include, e.g., GET-Request (retrieves one or more values from a managed object), SET-Request (updates selected variables of a managed object), and GET-Response (a reply to a GET-Request or a SET-Request). SNMP commands—including requests and responses—are sent between network management systems and managed devices as SNMP messages. An SNMP message is an SNMP protocol data unit (PDU) that includes message header elements defined by a particular Request for Comments (RFC).

When an SNMP command fails, a network management system typically sends an SNMP error code back to a user—e.g., a human network administrator. However, SNMP provides only a limited number of error codes. For version 1 of SNMP (SNMPv1), the following five error codes are supported: tooBig(1), noSuchName(2), badValue(3), readOnly(4), and genErr(5). See RFC 1157, Case, May 1990, A Simple Network Management Protocol (SNMP), incorporated herein by reference. For version 2 of SNMP (SNMPv2), the following 18 error codes are supported: tooBig(1), noSuchName(2), badValue(3), readOnly(4), and genErr(5), noAccess(6), wrongType(7), wrongLength(8), wrongEncoding(9), wrongValue(10), noCreation(11), inconsistentValue(12), resourceUnavailable(13), commitFailed(14), undoFailed(15), authorizationError(16), notWritable(17), and inconsistentName(18). See RFC 1905, Case, January 1996, Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2), incorporated herein by reference.

In some cases, more specific information about an error is known when an SNMP command fails. However, when a conventional SNMP protocol is used, the specific information about the error is not passed back to a user. Instead, the specific information about the error is converted (or mapped) into an error code that can generally only notify a user that a particular type of error has occurred. The error code typically does not convey why the error occurred. For example, an error code of wrongValue in response to a failed SNMP SET-Request command does not convey why the value associated with the SNMP SET-Request is wrong.

SUMMARY

In general, in one aspect, this specification describes a method for processing a network management protocol command at a managed device in a network. The method includes receiving a network management protocol command at a managed device in a network, and determining whether the network management protocol command was processed successfully at the managed device. If the network management protocol command was not processed successfully at the managed device, then the method further includes storing data related to the network management protocol command that was not processed successfully at the managed device.

Particular implementations can include one or more of the following features. Storing data can include storing diagnostic text information related to the network management protocol command that was not processed successfully at the managed device. The method can further include generating the diagnostic text information related to the network management protocol command that was not processed successfully at the managed device. Receiving a network management protocol command can include receiving a network management protocol command from a network management system in the network.

The method can further include sending, from the managed device, an error code associated with the network management protocol command that was not processed successfully to the network management system. Receiving a network management protocol command can include receiving an SNMP protocol command. Sending an error code can include sending one of a plurality of SMNP error codes of an SNMPv1 standard or an SNMPv2 standard. Storing diagnostic text information can include storing a string of text representing a reason why the network management protocol command was not processed successfully. Storing diagnostic text information can also include generating a diagnostic object associated with the network management protocol command that was not processed successfully, and storing the diagnostic text information in the diagnostic object. Generating a diagnostic object can include generating a diagnostic table object. Storing the diagnostic text information can include storing the diagnostic text information within the diagnostic table object. Storing the diagnostic text information within the diagnostic table object can include storing the diagnostic information based on at least two keys. The first key represents an identifier of the network management system that issued the network management protocol command that was not processed successfully, and the second key represents an identifier of the network management protocol command that was not processed successfully. Each of the first key and the second key can represent an index for locating a logical row in the diagnostic table object.

The method can further include receiving, from the network management system, a second network management protocol command containing an object identifier that identifies the diagnostic table object that contains diagnostic text information related to the network management protocol command that was not processed successfully, retrieving the diagnostic text information from the diagnostic table object, and sending the diagnostic text information to the network management system. Receiving a network management protocol command at a managed device can include receiving a network management protocol command at a device that includes a network interface. Receiving a network management protocol command at a device that includes a network interface can include receiving a network management protocol command at one of a host, router, bridge, computer, modem, or terminal server.

In general, in another aspect, this specification describes a method for processing a request for information related to a network management protocol command through a network management system. The method includes receiving an application request from a requestor for information associated with a previously sent network management protocol command that was not processed successfully at a managed device, configuring the application request into a second network management protocol command, sending the second network management protocol command from the network management system to the managed device, and receiving diagnostic text information from the managed device responsive to the request.

Particular implementations can include one or more of the following features. The method can further include displaying the diagnostic text information to the requestor, and deleting the diagnostic text information at the managed device. Configuring the application request can include configuring the application request into an SNMP command. Configuring the application request into an SNMP command can include configuring an SNMP command containing an object identifier identifying a diagnostic object that contains the diagnostic text information.

The method can further include setting an identifier for the network management system at the managed device, the managed device using the identifier of the network management system to store the diagnostic text information. Setting an identifier for the network management system can include setting the identifier to be one the following: (1) an IP (Internet Protocol) address associated with the network management system, (2) a user name/community name corresponding to the network management system, or (3) a concatenation of an IP address and a user name/community of the network management system. The method can further'include setting an identifier of the previously sent network management protocol command that was not processed successfully at a managed device. The managed device uses the identifier of the network management system to store the diagnostic text information.

In general, in another aspect, this specification describes a managed device in a network. The managed device includes an agent operable to receive a network management protocol command, and an execution engine operable to determine whether the network management protocol command was processed successfully. If the network management protocol command was not processed successfully at the managed device, the managed device further includes an indexing engine operable to store, within a storage device, data related to the network management protocol command that was not processed successfully.

In general, in another aspect, this specification describes a network management system in a network. The network management system includes: a manager operable to receive an application request from a requestor for information associated with a previously sent network management protocol command that was not processed successfully at a managed device in the network; a request processor operable to configure the application request into a second network management protocol command; and an encapsulation engine operable to send the second network management protocol command, from the network management system to the managed device. The manager is further operable to receive diagnostic text information from the managed device responsive to the request.

Implementations can include one or more of the following advantages. A method and apparatus is provided for managing a network using one or more diagnostic objects in a Management Information Base (MIB). The one or more diagnostic objects include a diagnostic table object for storing diagnostic text information. The diagnostic text information relates to failed transactions generated by, in one implementation, SNMP agents of managed devices. A network management system can access the diagnostic table object and provide the diagnostic text information to a user. Advantageously, errors generated by an agent do not have to be translated (or mapped) into an error code, e.g., SNMP error codes or any other error codes. A network administrator can, therefore, obtain a greater amount of information as to why an SNMP command failed.

The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will be apparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of a management portion of a managed network.

FIG. 2 is block diagram of device architectures of a network management system and a managed device.

FIG. 3 is a flowchart illustrating a method for managing the network of FIG. 1.

FIG. 4 illustrates a diagnostic object.

FIG. 5 is a flowchart illustrating a method for retrieving diagnostic information of a failed transaction in the network of FIG. 1.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 illustrates a block diagram of a network 100. Network 100 includes a network management system 102, a first managed device 104, a second managed device 106, and a third managed device 108. Though one network management system 102 and three managed devices 104-108 are illustrated in FIG. 1 by way of example, network 100 can contain a different number of network management systems and/or managed devices.

Network 100 also includes a network medium 110 operable to carry communication messages between network management system 102 and managed devices 104-108. Network medium 110 can be any suitable communication medium—e.g., high-frequency coaxial cable, twisted pair cable, fiber optic cable, wireless links, and so on. In addition to the physical connection (i.e., network medium 110), a communication protocol is used to facilitate communication between network management system 102 and managed devices 104-108. In one implementation, network 100 uses a media access control (MAC) protocol to communicate data. Types of MAC protocols include, for example, Ethernet, token ring, Fiber Distributed Data Interface (FDDI), Cells In Frames (CIF), and other data link layer protocols.

Network management system 102 can be a computer that includes an SNMP manager 112 for managing network 100. In one implementation, SNMP manager 112 manages network 100 using the SNMP protocol.

Managed devices 104-108 can include any device that communicates over a network. Examples of such devices include hosts, routers, terminal servers, bridges, computers, modems, and other devices having a network interface. In one implementation, managed devices 104-108 respectively include SNMP agents 114-118 and MIBs 120-124. Each of SNMP agents 114-118 accesses and modifies corresponding managed objects (discussed in greater detail below) within MIBs 120-124 in response to SNMP commands from network management system 102. In one implementation, the managed objects include one or more diagnostic objects (discussed in greater detail below) that are operable to store diagnostic text information corresponding to failed SNMP commands, and provide the diagnostic text information to an SNMP manager, e.g., SNMP manager 112. In one implementation, the diagnostic objects are generated at run-time by one or more of SNMP agents 114-118 as a byproduct of a failed SNMP command. The diagnostic objects can be defined according to a diagnostic MIB module associated with MIBs 120-124.

FIG. 2 shows device architecture block diagrams for network management system 102 and managed device 104 in one implementation. Network management system 102 includes a management application 200. Management application 200 includes a user interface 202 and SNMP manager 112.

Management application 200 is a network management application that provides a user interface 202 for receiving application requests from a requestor (e.g., a network administrator or computer), and for providing information about network 100 to the requestor. An application request includes requests by the requestor to perform network management-related tasks on a managed device, e.g., managed devices 104-108. For example, a requestor may use manager application 200 to request diagnostic text information related to a failed SNMP command at managed device 104. To support requests, management application 200 includes a retrieval routine (e.g., SNMP manager 112) that retrieves the requested information. In one implementation, SNMP manager 112 includes a request processor 204, an encapsulation engine 206, a naming engine 208, a settings engine 210, and a diagnostic deletion engine 212.

Request processor 204 is operable to generate one or more network management protocol requests for, inter alia, retrieving diagnostic text information from a managed device (e.g., managed device 104) based on application requests. In one implementation, request processor 204 generates network management protocol requests including SNMP commands to retrieve diagnostic text information from a managed device. The SNMP commands can include, for example, GET-Requests, SET-Requests, and GET-Responses.

Encapsulation engine 206 is operable to encapsulate network management protocol requests (e.g., SNMP commands generated by request processor 204) into one or more protocol data unit (PDU) packets. In one implementation, encapsulation engine 206 is also operable to send PDU packets to one or more managed devices through one or more network layers and a physical layer.

Naming engine 208 is operable to set an identifier (ID) for a network management system (e.g., network management system 102). The ID for a network management system can be set within a managed object at each managed device in a network. In one implementation, a network management system has an ID based on: (1) an IP (Internet Protocol) address associated with the network management system, (2) a user name/community name corresponding to the network management system, or (3) both an IP address and a user name/community of the network management system combined—i.e., a concatenation of the network management system's IP address and user name/community name.

Naming engine 208 is further operable to set an ID of each SNMP command (e.g., GET, GET NEXT, GET BULK and SET) sent by a network management system. In one implementation, the ID of each SNMP command is set within a managed table object. The managed table object is operable to store IDs of several SNMP commands of a network management system that issues several SNMP commands prior to listening to a response. Alternatively, the ID of an SNMP command can be set within a managed object that does not have a tabular format.

Settings engine 210 is operable to set a duration (or time period) for how long a managed device maintains various settings (of managed objects) set by a network management system. The settings includes, e.g., an ID of a network management system, an ID of an SNMP command, and other settings set by a network management system. The time periods can be maintained within a managed object at each managed device. The time periods can be set according to any convenient granularity—e.g., seconds, minutes, hours, and so on.

Diagnostic deletion engine 212 is operable to delete diagnostic text information stored within a diagnostic object. Diagnostic objects are discussed in greater detail below. Diagnostic text information stored within a diagnostic object can be deleted to free resources of a managed device.

FIG. 2 also shows managed device 104 in greater detail. Managed device includes MIB 120 and SNMP agent 114. In one implementation, SNMP agent 114 includes an SNMP execution engine 216, an encapsulation engine 218, a textual engine 220, an indexing engine 222, and an error code generator 224.

SNMP execution engine 216 is operable to execute one or more received SNMP commands of a network management system (e.g., network management system 102).

Encapsulation engine 218 is operable to encapsulate network management protocol replies (e.g., SNMP GET-Response replies) generated by managed device 104 into one or more PDU packets. In one implementation, encapsulation engine 218 is further operable to send PDU packets to one or more network management systems through one or more network layers and a physical layer.

Textual engine 220 is operable to generate diagnostic text information corresponding to a failed SNMP command at managed device 104. Diagnostic text information generally includes descriptive information as to why a given SNMP command failed. The descriptive information can be stored as a string of text. In one implementation, multi-line diagnostic text information is generated by textual engine 220. Example diagnostic text information (in the management of routing tables) include “Destination Address for Route is not valid”, “IP mask does not cover the destination address”, and “Only a directly connected router can be defined as the gateway”. An SNMP error code that corresponds to each of the examples above is wrongValue, which does not convey as much information as the diagnostic text information.

Indexing engine 222 is operable to index (or store) diagnostic text information within a storage device, e.g., a Management Information Base (MIB). In one implementation, indexing engine stores the diagnostic text information in a diagnostic object (discussed in greater detail below). In one implementation, indexing engine 222 indexes diagnostic text information according to an ID of a network management system that issued the failed SNMP command and according to an ID of the particular failed SNMP command.

Error code generator 224 is operable to generate an SNMP error code corresponding to a failed SNMP command. In one implementation, an error code is sent to, e.g., a network administrator to inform the network administrator that a previously sent SNMP command has failed at a given managed device. The network administrator may then issue a request through management application 200 to retrieve diagnostic text information corresponding to the failed SNMP command.

For example, the request processor 204 can configure a GET-Request command that includes an object identifier identifying a diagnostic object or variable (that contains the diagnostic text information related to the failed SNMP command) to be retrieved from managed device 104. Encapsulation engine 206 encapsulates the Get-Request command in a PDU packet and sends the GET-Request command to managed device 104, e.g., through one or more network layers and a physical layer (not shown).

The GET-Request command is received at managed device 104, e.g., through one or more network layers and a physical layer (not shown). SNMP execution engine 216 executes the GET-Request command and obtains diagnostic text information related to the failed SNMP command from a diagnostic object (not shown) within MIB 120. In one implementation, MIB 120 includes a diagnostic MIB module (not shown) that contains one or more diagnostic objects. The diagnostic MIB module is associated with a private MIB of managed device 104.

The diagnostic text information is then sent back to network management system 102 in a GET-Response reply. For example, encapsulation engine 218 can encapsulate the GET-Response reply in a PDU packet and send the GET-Response reply to network management system 102, e.g., through one or more network layers and a physical layer (not shown).

The GET-Response reply is received at network management system 102. Management application 200 can provide the GET-Response reply, including the diagnostic text information related to the failed SNMP command, to a requestor (e.g., through user interface 202 of management application 200).

FIG. 3 illustrates a process 300 for managing application requests in network 100 (FIG. 1). An application request is received (step 302). An application request is a request from a requestor to perform one or more network management-related tasks on a managed device (e.g., managed device 104 of FIG. 1) in a network. The application request can be received based on a requestor executing a command through, for example, management application 200 (FIG. 2). The application request is configured into an SNMP command (step 306). In one implementation, a request processor (e.g., request processor 204 of FIG. 2) configures the application request into an SNMP command—e.g., a SET-Request command. The application request can be configured into other types of management protocol commands depending upon management protocol requirements of a network. For example, other types of management protocols include protocols that support managed information structures in Abstract Syntax Notation One (ASN.1)—e.g., Common Management Information Protocol (CMIP).

A determination is made whether the SNMP command was processed successfully at a managed device (step 306). In one implementation, an SNMP execution engine (e.g., execution engine 216 of FIG. 2) determines whether an SNMP command was successfully processed at the managed device. If the SNMP command was successfully processed at the managed device, then a determination is made whether there are any other application requests (step 308). If there are more application requests then process 300 returns to step 302. If there are no more application requests then process 300 ends (step 314).

If the SNMP command was not successfully processed at a managed device, then an error code is returned, e.g., to a requestor (step 310). In one implementation, an error code generator (e.g., error code generator 224 of FIG. 2) returns an error code to a requestor through a network management system. The error code can include, for example, one or more of the five SNMP error codes associated with SNMPv1, the eighteen SNMP error codes associated with SNMPv2, and other error codes generated by, e.g., software applications running at the managed device.

Diagnostic text information about the failed SNMP command is stored (step 312). In one implementation, an indexing engine (e.g., indexing engine 222 of FIG. 2) stores the diagnostic text information in a diagnostic object contained within an MIB of the managed device. The diagnostic objects can be generated during run-time as a byproduct of a failed SNMP command. The diagnostic text information generally contains information about why an SNMP command failed. For example, the diagnostic information generally includes text information that is useful for a requestor, such as a network administrator, to understand and correct errors associated with a failed SNMP command. In one implementation, a line number representing a location in software code where the SNMP command failure occurred is also stored within a diagnostic object.

In one implementation, the diagnostics objects include diagnostic table objects 400 for storing diagnostic text information, as shown in FIG. 4. In one implementation, a diagnostic table object 400 has (2) keys 402, 404 that are used to index diagnostic text information 406 for storage and retrieval purposes. A key represents an index for locating a particular logical row in diagnostic table object 400 in which diagnostic text information 406 is stored. In one implementation, the first key 402 represents the ID of the network management system that issued the failed SNMP command. As discussed above, a network management system can be identified by an IP address, user/community name, or both by IP address and user/community name. In one implementation, first key 402 is implicit (or hidden)— i.e., not part of the formal definition of diagnostic table object 400. Because a network may include several network management systems, making first key 402 implicit prevents one network management system from retrieving diagnostic text information of another network management system's failed SNMP command—i.e., a given network management system can only access diagnostic text information that is indexed according to that network management system's particular ID.

The second key 404 can represent the ID of a particular SNMP command. In one implementation, an SNMP command is identified according to the request-ID field in the SNMP PDU corresponding to the SNMP command. Alternatively, the ID of a given SNMP command can be identified according to the ID given to the particular SNMP command by a naming engine (e.g., naming engine 208 of FIG. 2) of a network management system (e.g., network management system 102).

FIG. 5 illustrates a process 500 for retrieving diagnostic text information in a network (e.g., network 100 of FIG. 1). An application request for diagnostic information is received (step 502). The application request for diagnostic information can be received based on a requestor, e.g., a network administrator, executing a command through management application 200 (FIG. 2). In one implementation, a requestor is notified that a previously sent SNMP command failed by the request for receiving an SNMP error code through user interface 202 of management application 200 (FIG. 2). The application request for diagnostic information is configured into an SNMP command (step 504). In one implementation, request processor 204 (FIG. 2) configures the application request for diagnostic information into an SNMP GET-Request command. In one implementation, the GET-request command contains an object identifier that identifies a diagnostic table object (within an MIB of a managed device) that contains diagnostic text information related to a previously sent failed SNMP command. In one implementation, the diagnostic text information is retrieved from the diagnostic table object according to the ID of the network management system and the ID of the particular failed SNMP command.

Diagnostic text information is returned (step 506). In one implementation, diagnostic text information retrieved from a diagnostic table object is displayed to a requestor through user interface 202 of management application 200 (FIG. 2). Optionally, the diagnostic text information can be deleted (e.g., using diagnostic deletion engine 212 of FIG. 2) once the diagnostic text information is displayed to the requestor. A determination is made whether there are any more application requests for diagnostic information (step 508). If there are more application requests for diagnostic information then process 500 returns to step 502. If there are no more application requests for diagnostic information then process 500 ends (step 510).

The invention can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The invention can be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

Method steps of the invention can be performed by one or more programmable processors executing a computer program to perform functions of the invention by operating on input data and generating output. Method steps can also be performed by, and apparatus of the invention can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array), an ASIC (application-specific integrated circuit), or discrete components or combinations thereof.

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in special purpose logic circuitry.

A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made. For example, the diagnostic objects can be used to store text strings other than error information. The diagnostic text information can also provide warnings or other information related to a given network management protocol command (e.g., an SNMP request). In such a case, a network management system can retrieve the diagnostic text information even when the network management protocol command was successful. Also, any other network connectivity/efficiency checking commands issued via a network management protocol (e.g., SNMP) can place results of corresponding commands in textual form within one or more diagnostic object, including diagnostic table objects.

Accordingly, other implementations are within the scope of the following claims. 

1. A method for managing a network, the network including one or more network management systems and one or more managed devices, the one or more network management systems operable to control the one or more managed devices, the method comprising: receiving an application request from a requestor to perform a network management-related task at a managed device; configuring the application request into an SNMP command to be performed by the managed device; processing the SNMP command at the managed device; determining whether the SNMP command was processed successfully at the managed device; if the SNMP command was not processed successfully at the managed device, then sending an SNMP error code from the managed device to the requestor; and storing diagnostic text information related to the SNMP command that was not processed successfully at the managed device.
 2. The method of claim 1, wherein sending an SNMP error code includes sending one of a plurality of SNMP error codes of an SNMPv1 standard or an SNMPv2 standard.
 3. The method of claim 1, wherein storing diagnostic text information includes: generating a diagnostic object associated with the SNMP command that was not processed successfully; and storing the diagnostic text information in the diagnostic object.
 4. The method of claim 3, wherein: generating a diagnostic object includes generating a diagnostic table object; and storing the diagnostic text information includes storing the diagnostic text information within the diagnostic table object.
 5. The method of claim 4, wherein storing the diagnostic text information within the diagnostic table object includes storing the diagnostic information based on at least two keys, the first key representing an identifier of a network management system that issued the SNMP command that was not processed successfully, and the second key representing an identifier of the SNMP command that was not processed successfully.
 6. The method of claim 5, wherein each of the first key and the second key represents an index for locating a logical row in the diagnostic table object.
 7. The method of claim 4, further comprising: receiving a second application request from the requestor for diagnostic information related to the SNMP command that was not processed successfully; configuring the second application request into an SNMP command, the SNMP command containing an object identifier that identifies the diagnostic object that contains diagnostic text information related to the SNMP command that was not processed successfully; retrieving the diagnostic text information from the diagnostic object; and displaying to the requestor the diagnostic text information.
 8. A system for managing a network, the network including one or more network management systems and one or more managed devices, the one or more network management systems operable to control the one or more managed devices, the system comprising: a management application configured to receive an application request from a requestor to perform a network management-related task at a managed device, the management application being associated with a network management system; a request processor configured to configure the application request into an SNMP command to be performed by the managed device; an SNMP execution engine configured to process the SNMP command at the managed device and determine whether the SNMP command was processed successfully at the managed device; an error code generator configured to send an SNMP error code from the managed device to the requestor if the SNMP command was not processed successfully at the managed device; and an indexing engine configured to store diagnostic text information related to the SNMP command that was not processed successfully at the managed device.
 9. The system of claim 8, wherein the SNMP error code is one of a plurality of SNMP error codes of an SNMPv1 standard or an SNMPv2 standard.
 10. The system of claim 8, further comprising: an SNMP agent operable to generate a diagnostic object associated with the SNMP command that was not processed successfully; and wherein, the indexing engine is operable to store the diagnostic text information in the diagnostic object.
 11. The system of claim 10, wherein: the diagnostic object is a diagnostic table object; and the indexing engine is operable to store the diagnostic text information in the diagnostic table object.
 12. The system of claim 11, wherein the indexing engine is operable to store the diagnostic text information in the diagnostic table object based on at least two keys, the first key representing an identifier of a network management system that issued the SNMP command that was not processed successfully, and the second key representing an identifier of the SNMP command that was not processed successfully.
 13. The system of claim 12, wherein each of the first key and the second key represents an index for locating a logical row in the diagnostic table object.
 14. The system of claim 11, wherein: the management application is operable to receive a second application request from the requestor for diagnostic information related to the SNMP command that was not processed successfully; the request processor is operable to configure the second application request into an SNMP command, the SNMP command containing an object identifier that identifies the diagnostic object that contains diagnostic text information related to the SNMP command that was not processed successfully; the request processor operable to retrieve the diagnostic text information from the diagnostic object; and the management application further operable to display to the requestor the diagnostic text information.
 15. A system for managing a network, the network including one or more network management systems and one or more managed devices, the one or more network management systems operable to control the one or more managed devices, the system comprising: means for receiving an application request from a requestor to perform a network management-related task at a managed device; means for configuring the application request into an SNMP command to be performed by the managed device; means for processing the SNMP command at the managed device; means for determining whether the SNMP command was processed successfully at the managed device; if the SNMP command was not processed successfully at the managed device, then means for sending an SNMP error code from the managed device to the requestor if the SNMP command was not processed successfully at the managed device; and means for storing diagnostic text information related to the SNMP command that was not processed successfully at the managed device.
 16. The system of claim 15, wherein the means for sending an SNMP error code includes means for sending one of a plurality of SNMP error codes of an SNMPv1 standard or an SNMPv2 standard.
 17. The system of claim 15, wherein the means for storing diagnostic text information includes: means for generating a diagnostic object means associated with the SNMP command that was not processed successfully; and means for storing the diagnostic text information in the diagnostic object means.
 18. The system of claim 17, wherein: the means for generating a diagnostic object means includes means for generating a diagnostic table object means; and the means for storing the diagnostic text information includes means for storing the diagnostic text information within the diagnostic table object means.
 19. The system of claim 18, wherein the means for storing the diagnostic text information within the diagnostic table object means includes means for storing the diagnostic information based on at least two key means, the first key means representing an identifier of a network management system that issued the SNMP command that was not processed successfully, and the second key means representing an identifier of the SNMP command that was not processed successfully.
 20. The system of claim 19, wherein each of the first key means and the second key means represents an index for locating a logical row means in the diagnostic table object means.
 21. The system of claim 18, further comprising: means for receiving a second application request from the requestor for diagnostic information related to the SNMP command that was not processed successfully; means for configuring the second application request into an SNMP command, the SNMP command containing an object identifier that identifies the diagnostic object means that contains diagnostic text information related to the SNMP command that was not processed successfully; means for retrieving the diagnostic text information from the diagnostic object means; and means for displaying to the requestor the diagnostic text information.
 22. A computer program stored on a computer storage medium comprising instructions when executed by a processor, causes the processor to receive an application request from a requestor to perform a network management-related task at a managed device; configure the application request into an SNMP command to be performed by the managed device; process the SNMP command at the managed device; determine whether the SNMP command was processed successfully at the managed device; if the SNMP command was not processed successfully at the managed device, then send an SNMP error code from the managed device to the requestor; and store diagnostic text information related to the SNMP command that was not processed successfully at the managed device.
 23. The computer program of claim 22, wherein the instructions to send an SNMP error code include instructions to send one of a plurality of SNMP error codes of an SNMPv1 standard or an SNMPv2 standard.
 24. The computer program of claim 22, wherein the instructions to store diagnostic text information include instructions to: generate a diagnostic object associated with the SNMP command that was not processed successfully; and store the diagnostic text information in the diagnostic object.
 25. The computer program of claim 24, wherein: the instructions to generate a diagnostic object include instructions to generate a diagnostic table object; and the instructions to store the diagnostic text information include instructions to store the diagnostic text information within the diagnostic table object.
 26. The computer program of claim 25, wherein the instructions to store the diagnostic text information within the diagnostic table object include instructions to store the diagnostic information based on at least two keys, the first key representing an identifier of a network management system that issued the SNMP command that was not processed successfully, and the second key representing an identifier of the SNMP command that was not processed successfully.
 27. The computer program of claim 26, wherein each of the first key and the second key represents an index for locating a logical row in the diagnostic table object.
 28. The computer program of claim 25, further comprising instructions to cause a programmable processor to: receive a second application request from the requestor for diagnostic information related to the SNMP command that was not processed successfully; configure the second application request into an SNMP command, the SNMP command containing an object identifier that identifies the diagnostic object that contains diagnostic text information related to the SNMP command that was not processed successfully; retrieve the diagnostic text information from the diagnostic object; and display to the requestor the diagnostic text information. 